Importing a repository configuration loads the settings from a repository that was previously exported as described in Exporting the configuration.
Importing a configuration is useful for several purposes:
The following table lists the configuration items that can be imported and describes how the items are imported.
Item | Description |
---|---|
Property definitions (document, tag, project) |
If an item already exists in the repository, it is skipped. |
Object types (document, tag, project) |
|
Reference types (document, tag) |
|
Filters (document, tag, project) |
|
Security settings
|
All security settings will be removed and replaced by the settings in the configuration file. If a user or group is missing, it will be ignored. This can happen when importing a configuration that was exported from a server with different users and groups. The memberships are applied to all projects. If a group already has global permissions, they are skipped. If a role is applied to a hierarchy value, the value is created so that the security will apply as expected when the value is used later. The value must not already exist. |
To import a configuration:
When the process has completed, the changes are effective immediately.
Related concepts
Related tasks
Configuring the BlueCielo File Publishing Service
Configuring a SharePoint server
Configuring the BlueCielo Project Portal Publishing Service
Configuring a Meridian Enterprise Server cluster
Related information